This is just an exploratory PR. If we want this, we'll at least need to update the Blueprints Builder as well.

Adding the smol-toml dependency adds 40K to the from the built wasm-wordpress-net/assets dir.

Thank you for exploring this! Let's hold on with merging for now, but let's keep it around for the time when we focus on the configuration more.

What I already like:

• It's just a different way of parsing the input
• The same validation mechanism works

What I wonder about:

• Can we make the input shape more ergonomic for TOML? Or is it fine now?
• Can we provide some TOML-specific niceties that we cannot in JSON?
• Would the above ideas translate neatly into the PHP Blueprints library?

smol-toml

❤️

Thank you for exploring this! Let's hold on with merging for now, but let's keep it around for the time when we focus on the configuration more.

That sounds good. Moved to "Future work".

What I already like:

• The same validation mechanism works

I like this too!

What I wonder about:

• Can we make the input shape more ergonomic for TOML? Or is it fine now?
• Can we provide some TOML-specific niceties that we cannot in JSON?

These are good questions. Offhand, it just seems like this is a more human-friendly format that can be parsed to a data structure that is similar to those derived from JSON and YAML. Is there anything particular you had in mind?

One possible drawback for TOML authoring is a lack of autocomplete support compared to what we get from JSON + JSON Schema. But it seems possible to use a JSON schema to hint at the expected structure of a TOML doc. This is discussed a bit here in the TOML repo.

smol-toml

❤️

😄